Performing searches using computing devices equipped with pressure-sensitive displays

ABSTRACT

Techniques include receiving a pressure input from a user of a user device at a pressure-sensitive display of the device and determining that the display is covered (e.g., obscured from the user&#39;s view) using the device. The techniques further include, in response to receiving the pressure input and determining that the display is covered, receiving a search query from the user at the device via voice input, transmitting the query to a search system via a network using the device, and receiving search results from the system at the device subsequent to transmitting the query. The techniques also include performing one or more actions associated with the search results using the user device (e.g., displaying the results to the user at the display, providing a text-to-speech or playback output for the results to the user, and/or forwarding the results to another computing device for display and/or text-to-speech or playback output).

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional Application No.62/215,492 filed Sep. 8, 2015, which is hereby incorporated by referencein its entirety.

TECHNICAL FIELD

This disclosure generally relates to the field of computing devices, andmore particularly to techniques for interacting with touchscreen-enabledcomputing devices.

BACKGROUND

In recent years, the use of computers, tablets, smartphones, smartwatches, and other stationary and mobile computing devices has grownsignificantly. Additionally, the inclusion of various touchscreentechnologies configured to receive user inputs at display screens ofthese and other computing devices has also increased. Today, manyconsumer and industrial computing devices and appliances are capable ofreceiving user inputs at display screens via any of a variety ofdifferent touchscreen technologies, including resistive, capacitive,surface-acoustic-wave (SAW), optical, acoustic, as well as any othertouchscreen technologies or types.

SUMMARY

In one example, a computing device includes a pressure-sensitive displayconfigured to receive a pressure input from a user of the device, avoice input module configured to receive a search query from the uservia voice input, a network interface component configured to communicatewith a network, one or more memory components configured to storecomputer-readable instructions, and one or more processing unitsconfigured to execute the instructions. The computer-readableinstructions, when executed by the processing units, cause the units toreceive the pressure input from the user at the pressure-sensitivedisplay, determine that the display is covered, and, in response toreceiving the input and determining that the display is covered, receivethe search query from the user using the voice input module. Thecomputer-readable instructions further cause the processing units totransmit the search query to a search system via the network using thenetwork interface component, receive search results from the systemsubsequent to transmitting the query, and perform an action associatedwith the results.

In another example, a method includes receiving a pressure input from auser of a user device at a pressure-sensitive display of the device,determining that the display is covered using the device, and, inresponse to receiving the input and determining that the display iscovered, receiving a search query from the user at the device via voiceinput. The method further includes transmitting the search query to asearch system via a network using the user device, receiving searchresults from the system at the device subsequent to transmitting thequery, and performing an action associated with the results using thedevice.

BRIEF DESCRIPTION OF DRAWINGS

The details of one or more examples are set forth in the accompanyingdrawings and the description below. Other features, objects, andadvantages will be apparent from the description and drawings, and fromthe claims.

FIGS. 1A-1B illustrate example user devices that may be used toimplement the techniques of the present disclosure.

FIGS. 2A-2D are conceptual diagrams of example user interactions withdisplays of user devices, consistent with the techniques of thisdisclosure.

FIG. 3 illustrates an example environment that includes a user deviceand a search system that communicate via a network.

FIG. 4 is a functional block diagram of an example user device incommunication with a user and a search system.

FIG. 5A is a functional block diagram of an example search system.

FIG. 5B is a functional block diagram of an example search module.

FIG. 6 illustrates an example record included in an example search datastore.

FIGS. 7A-7C are flow diagrams that illustrate example methods forperforming a search using a user device in response to receiving apressure input at a pressure-sensitive display of the device anddetermining that the display is covered.

FIG. 8 is a flow diagram that illustrates an example method forperforming a search for records using a search system based on a searchquery received from a user device.

FIGS. 9A-10B illustrate example graphical user interfaces (GUIs) thatmay be generated on a user device according to this disclosure.

DETAILED DESCRIPTION

The figures and the following description relate to exampleimplementations by way of illustration only. It should be noted thatfrom the following discussion, alternative implementations of thestructures and methods disclosed herein will be readily recognized asviable alternatives that may be employed without departing from thescope of this disclosure.

The present disclosure generally relates to the field of computingdevices, and, more particularly, to techniques for interacting withcomputing devices equipped with pressure-sensitive displays (e.g.,laptops, tablets, smartphones, smart watches, and fitness bands).Specifically, the techniques of this disclosure are directed tocomputing devices configured to receive inputs from users viapressure-sensitive displays capable of detecting (e.g., sensing)pressure inputs from the users. For example, to receive the pressureinputs, the pressure-sensitive displays may each include one or more ofa resistive touchscreen, a push-button-based touchscreen, and anotherpressure-sensitive sensor or input device. In some examples, thepressure-sensitive displays described herein may also be configured todetect (e.g., sense) other types of inputs from the users, such asfinger contact inputs. For instance, to receive the finger contactinputs from the users, the pressure-sensitive displays may each includeone or more of a capacitive touchscreen and another fingercontact-sensitive sensor or input device.

In general, the techniques described herein may enable users to interactwith computing devices that include pressure-sensitive displays ininstances where the displays are covered (e.g., obscured from the users'view by one or more layers of clothing or other objects). In particular,the techniques may include receiving a pressure input from a user at apressure-sensitive display of a user device. The techniques may furtherinclude determining that the pressure-sensitive display is covered. Forexample, determining that the pressure-sensitive display is covered maybe performed using the received pressure input and/or other information(e.g., an output of an ambient light sensor included in the userdevice). In this disclosure, receiving the pressure input anddetermining that the pressure-sensitive display is covered may bereferred to as detecting a “covered user interaction.” The techniquesmay also include, in response to receiving the pressure input anddetermining that the pressure-sensitive display is covered (e.g., inresponse to detecting a covered user interaction), performing any of avariety of actions using the user device, as described herein. Using thedescribed techniques may, in some examples, improve the user'sexperience when interacting with the user device.

As one example, the pressure-sensitive display of the user device may becovered by the user's clothing (e.g., by sleeve or pocket fabric) orother objects, thereby preventing the user from interacting with thedisplay. For example, the pressure-sensitive display being covered mayprevent the user from entering search queries into a search application(app) executing on the user device (e.g., using a capacitive touchscreenincluded in the display, or a keypad included in the device) andperforming searches using the device. In this example, in response toreceiving the pressure input and determining that the pressure-sensitivedisplay is covered, as described herein, the user device may furtherreceive, via voice input, a search query from the user. For example, theuser device may first provide a user prompt (e.g., a sound and/orvibration output) to the user requesting that the user provide thesearch query and subsequently receive the query from the user inresponse to providing the prompt. In this example, the user device maythen transmit the search query to a search system, receive searchresults from the system in response to transmitting the query, andperform one or more actions associated with the results. As one example,the user device may display the search results to the user at thepressure-sensitive display (e.g., assuming that the display is no longercovered). As another example, the user device may provide atext-to-speech or playback output for the search results (e.g., fortext-based search results and/or search results including an audiocomponent) to the user. As still another example, the user device mayforward the search results to another computing device (e.g., fordisplay and/or text-to-speech or playback output).

In this manner, the techniques described herein may improve a user'sexperience when using a user device that includes a coveredpressure-sensitive display by avoiding the inconvenience associated withthe user uncovering the display in order to interact with the device.For example, as described herein, the techniques may enable the user tospecify search queries using voice input and perform searches using thequeries and the user device, despite the pressure-sensitive displaybeing covered, or otherwise obscured from the user's view.

FIGS. 1A-1B illustrate example user devices 100 that may be used toimplement the techniques of this disclosure. As shown in FIG. 1A, theuser device 100 may be a smart watch computing device configured to beworn around a user's wrist and capable of being covered by the user'sshirt sleeve. Alternatively, as shown in FIG. 1B, the user device 100may be a smartphone computing device configured to be held in a user'shand and capable of being stored in the user's pocket. In otherexamples, the user device 100 may be a tablet, a laptop computer, or adesktop computer. In still other examples, the user device 100 may be acomputing device having another form factor, such as a computing deviceincluded in a vehicle, a gaming device, a television, or anotherappliance (e.g., a networked home automation device or appliance). Ingeneral, the user device 100 of this disclosure may be any computingdevice that includes a pressure-sensitive display 102 configured toreceive pressure inputs (e.g., a display that includes a resistive orpush-button-based touchscreen) from users of the device 100, asdescribed herein. In other words, the pressure-sensitive display 102 maybe configured to receive pressure inputs having any non-zero amount ofpressure, or force per unit of area, from the users using any of one ormore fingers of the users' hands, other parts of the users' bodies, andother objects that are not part of the users' bodies (e.g., styli),irrespective of whether the body part or object used is electricallyconductive. Additionally, or alternatively, the pressure-sensitivedisplay 102 may be configured to receive the pressure inputs from theusers via an accelerometer sensor included in the user device 100 thatdetects force (e.g., in the form of so-called finger “taps,” or shaking)applied to the display 102 using fingers of the users' hands, otherparts of the users' bodies, and/or other objects that are not part ofthe users' bodies, also irrespective of the body part or object usedbeing electrically conductive. In other words, the accelerometer sensormay provide an output that indicates a pressure input received at thepressure-sensitive display 102. In further examples, as describedherein, the pressure-sensitive display 102 may also be configured toreceive finger contact inputs (e.g., the display 102 may include acapacitive touchscreen configured to detect user finger contact, such asfinger taps and so-called finger “swipes”). For example, thepressure-sensitive display 102 may be configured to receive fingercontact inputs, which may or may not include a pressure or forcecomponent, from the users using any of fingers of the users' hands,other parts of the users' bodies (e.g., portions of the users' palms),and other objects that are not part of the users' bodies (e.g.,conductive styli), so long as the body parts or objects used aresubstantially electrically conductive.

The user device 100 may use various different operating systems orplatforms. In examples where the user device 100 is a mobile device(e.g., a smart watch or a smartphone), the device 100 may operate usingan operating system (OS) such as ANDROID® by Google Inc., IOS® by AppleInc., or WINDOWS PHONE® by Microsoft Corporation. In examples where theuser device 100 is a laptop or desktop computer, the device 100 may usean OS such as MICROSOFT WINDOWS® by Microsoft Corporation, MAC OS® byApple Inc., or LINUX® (LINUX is the registered trademark of LinusTorvalds in the U.S. and other countries). The user device 100 may alsointeract with users and/or other devices or systems using operatingsystems other than those described herein, whether presently availableor developed in the future.

FIGS. 2A-2D are conceptual diagrams of example user interactions withpressure-sensitive displays 102 of user devices 100, consistent with thetechniques of this disclosure. The user device 100 depicted in FIG. 2Ais a smart watch computing device. The user device 100 of FIG. 2Aincludes a pressure-sensitive display 102 capable of receiving pressureinputs 206 from users of the device 100. In particular, as shown in FIG.2A, the pressure-sensitive display 102 may be configured to detect(e.g., sense) a pressing motion of one or more of a user's fingers,another part of the user's body, or an object that is not part of theuser's body with respect to the display 102. For instance, the pressingmotion may be in a direction that is substantially inward with respectto the pressure-sensitive display 102 and the user device 100 (e.g.,substantially into a plane of the display 102 and in a direction that issubstantially orthogonal to the plane). In other words, the pressingmotion may be substantially within a Z-axis relative to an X-Y planedefined by the surface of the display 102 and directed substantiallytoward the display 102.

In some examples, the pressure-sensitive display 102 may be configuredto detect a momentary pressing motion, or a push, lasting a relativelyshort time. In other examples, the pressure-sensitive display 102 may beconfigured to detect pressing motions lasting a specified duration oftime (e.g., to filter out errant or inadvertent presses on, or so-called“bumps” against, the user device 100). In further examples, thepressure-sensitive display 102 may be configured to detect the pressingmotion irrespective of the amount of pressure used. In other examples,the pressure-sensitive display 102 may be configured to detect pressingmotions having at least a specified threshold amount of pressure (e.g.,to filter out errant/inadvertent presses/bumps).

The pressure-sensitive display 102 of the user device 100 shown in FIG.2A is also capable of receiving finger contact inputs 202 and 204 fromthe users of the device 100. Specifically, as shown in FIG. 2A, thepressure-sensitive display 102 may be further configured to detect(e.g., sense) a tapping and/or lateral swiping motion of one or more ofthe user's fingers, another part of the user's body, or a substantiallyelectrically conductive object that is not part of the user's body withrespect to the display 102. As one example, the tapping motion may be ina direction that is substantially inward with respect to thepressure-sensitive display 102 and the user device 100, in a similarmanner as described with reference to the pressure input 206. In thisexample, the tapping motion may result in a finger contact with thepressure-sensitive display 102 in a particular area of the display 102(e.g., at a given point within an X-Y plane defined by the surface ofthe display 102). For example, the finger contact may provide a smallamount of pressure, or provide substantially no pressure, toward thepressure-sensitive display 102. The taping motion may be represented asa single point of finger contact with the pressure-sensitive display 102(e.g., at an intersection of X- and Y-components 202, 204 describedherein), as shown in FIG. 2A. As another example, the lateral swipingmotion may be in one or more directions that are each substantiallyparallel with respect to the pressure-sensitive display 102 and the userdevice 100 (e.g., substantially parallel to the X-Y plane defined by thesurface of the display 102). For example, the lateral swiping motion maybe in any direction within the X-Y plane. For instance, the lateralswiping motion may be represented as a motion vector including acombination of an X-component 202 of the motion in the X (e.g.,upward/downward) direction and a Y-component 204 of the motion in the Y(e.g., right/left) direction, as also shown in FIG. 2A. In this example,the lateral swiping motion may result in a finger contact with thepressure-sensitive display 102 along a range of distance spanning thedisplay 102, e.g., again without providing a significant amount ofpressure, or providing substantially no pressure, toward the display102. The user device 100 depicted in FIG. 2B is a smartphone computingdevice and includes the same or similar elements and user interactionsas those described with reference to the user device 100 shown in FIG.2A.

In the examples described herein, the pressure-sensitive display 102 ofthe user device 100 may be configured to receive any combination of thepressure inputs 206 and finger contact inputs 202, 204 from the users ofthe device 100 (e.g., as depicted by a so-called “cumulative user input”200 shown in FIGS. 2A-2D). In some examples, the pressure-sensitivedisplay 102 may receive a pressure input 206 from a user of the userdevice 100 without also receiving a finger contact input 202, 204 fromthe user. In these examples, the user device 100 may determine that thepressure-sensitive display 102 is covered (e.g., obscured from theuser's view by clothing or another object) by determining that thepressure input 206 does not coincide with any finger contact inputs 202,204 also received (e.g., substantially contemporaneously with thepressure input 206) from the user at the same display 102. Additionally,or alternatively, the user device 100 may determine that thepressure-sensitive display 102 is covered based on an output receivedfrom an ambient light sensor included in the device 100.

FIGS. 2C and 2D illustrate side-views of the user devices 100 describedwith reference to FIGS. 2A and 2B. As shown in each of FIGS. 2C and 2D,the pressure-sensitive display 102 of the user device 100 receives apressure input 206 from a user of the device 100. In each of theexamples of FIGS. 2C and 2D, the pressure-sensitive display 102 iscovered (e.g., obscured from the user's view) by one or more layers ofclothing or another object, which may be referred to herein as anobstruction 208. As further shown in each example, thepressure-sensitive display 102 receives the pressure input 206 from theuser through the obstruction 208. In other words, the pressure input 206passes (e.g., is relayed as a mechanical force) from one or more of theuser's fingers, another part of the user's body, or an object that isnot part of the user's body through the obstruction 208 and reaches thepressure-sensitive display 102. In these examples, although theobstruction 208 may provide some amount of electrical insulation betweenthe user's body part or object used to generate the pressure input 206and the pressure-sensitive display 102, the display 102 may receive theinput 206 from the user irrespective of whether the body part or objectused is electrically conductive.

In contrast, as also shown in each of FIGS. 2C and 2D, thepressure-sensitive display 102 does not receive a finger contact input202, 206 from the user. Stated another way, in instances where thepressure input 206 described herein originates from one or more of theuser's fingers, another part of the user's body, or a conductive objectthat is not part of the user's body, the pressure-sensitive display 102does not receive a corresponding finger contact input 202, 204 from theuser due to the obstruction 208. In these examples, because theobstruction 208 may provide some amount of electrical insulation betweenthe user's body part or object used to generate the finger contact input202, 204 and the pressure-sensitive display 102, the display 102 may notreceive (e.g., the obstruction 208 may block) the input 202, 204, eventhough the body part or object used is electrically conductive.

FIG. 3 is a functional block diagram illustrating an example environmentthat includes a user device 100 and a search system 104 that communicatevia a network 106. The network 106 through which the user device 100 andthe search system 104 communicate may include any type of network, suchas a local area network (LAN), a wide area network (WAN), and/or theInternet. As shown in FIG. 3, the search system 104 includes a searchmodule 108, a search data store 110, and a result generation module 112,which are described herein.

In the example of FIG. 3, the user device 100 initially receives apressure input 206 from a user of the device 100 at a pressure-sensitivedisplay 102 of the device 100 and determines that the display 102 iscovered, as described herein. In some examples, the user device 100 maysubsequently provide a user prompt to the user configured to prompt theuser to provide a search query to the device 100 via voice input. Inthis example, the user device 100 receives the search query from theuser via voice input (e.g., in response to providing the user prompt)and transmits the query to the search system 104. The search system 104receives the search query from the user device 100 and generates searchresults in response to receiving (e.g., based on) the query.Specifically, the search system 104 generates the search results basedon the search query and information included in one or more recordsstored in the search data store 110. In this example, each record mayinclude or reference content related to any of native apps, native appstates, websites (e.g., web pages), documents, and/or media (e.g.,audio, video, and/or image) files. In some examples, the informationincluded in the records may include one or more access mechanisms (AMs)that enable user devices 100 to access app states of native or web-basedapps specified by the records. In general, the information included orreferenced in each record may be referred to herein as result objectdata. The search system 104 transmits the result object data included inthe records (e.g., one or more files, or AMs) to the user device 100 asthe search results. The records may further include record information(e.g., text) and other information (e.g., record names/IDs associatedwith the records), which the search system 104 may use to identify therecords in the search data store 110, as described herein. The searchsystem 104 transmits the search results, including the result objectdata, to the user device 100. The user device 100 receives the searchresults from the search system 104. In some examples, the user device100 (or, e.g., another computing device) may display the search resultsto the user as one or more user selectable links that include the resultobject data, as described herein. In other examples, the user device 100(or, e.g., another computing device) may provide a text-to-speech orplayback output for the search results to the user, as also describedherein.

In this disclosure, an app may refer to computer software that causes acomputing device (e.g., a user device 100) to perform a task. In someexamples, an app may be referred to as a “program.” Example apps includeword processing apps, spreadsheet apps, messaging apps, media streamingapps, social networking apps, and games. Apps can be executed on avariety of different computing devices, including mobile computingdevices such as smartphones, tablets, and wearable computing devices(e.g., headsets and/or watches). Apps can also be executed on othertypes of computing devices having other form factors, such as laptopcomputers, desktop computers, or other consumer electronic devices. Insome examples, apps may be installed on a computing device prior to auser purchasing the device. In other examples, the user may download andinstall apps on the computing device after purchasing the device. Anative app, as used herein, may refer to an app that is installed andexecuted on a user device 100. A web-based app may refer to an app thatis accessible from a user device via a web browser app.

An AM, as used herein, may include any of a native app AM (hereinafter,“app AM,” or “AAM”), a web AM (hereinafter, “WAM”), and an app downloadaddress (ADA). As such, a user device 100 of the present disclosure mayuse an AM to access the functionality provided by a native or aweb-based app. For example, the user may select a user selectable linkthat includes the AM to access the functionality of the app. An AAM maybe a string that references a native app and indicates one or moreoperations for a user device 100 (e.g., the app) to perform. If a userof the user device 100 selects a user selectable link that includes theAAM, the device 100 may launch the native app referenced by the AAM and(e.g., cause the app to) perform the operations indicated by the AAM. Inother words, the user selecting the user selectable link may cause theuser device 100 to launch the native app and set the app into a state(e.g., in which the app displays a GUI) corresponding to the operations.As a result, the native app may be configured to display one or moreproducts, services, or vendors, to the user, e.g., via a display of theuser device 100. In this manner, the AAM may specify the state of thenative app. The state, in turn, may refer to the operations indicated bythe AAM and/or the outcome of the native app performing the operationsin response to the user selecting the user selectable link including theAAM. A WAM may include a resource identifier that references a webresource (e.g., a page of a web-based app, or web site). For example,the WAM may include a uniform resource locator (URL) (i.e., a webaddress) used with the hypertext transfer protocol (HTTP). If a user ofa user device 100 selects a user selectable link that includes the WAM,the device 100 may launch a web browser app included on the device 100and retrieve the web resource referenced by the resource identifier.Stated another way, if the user selects the user selectable link, theuser device 100 may launch the web browser app and access a state (e.g.,a page) of a web-based app, or website, specified by the WAM. In someexamples, a WAM included in a record along with an AAM may specify astate of a web-based app that is equivalent (e.g., analogous) to a stateof a native app specified by the AAM. An ADA may specify a location(e.g., a digital distribution platform, such as Google Play® by GoogleInc.) where a native app (e.g., a native app referenced by an AAM) maybe downloaded. In some examples, a record may include an ADA along withan AAM (and, e.g., a WAM). In these examples, the ADA may specify alocation from which a native app referenced by the AAM may bedownloaded.

In some examples, the search system 104 may transmit the search results,including the result object data, to the user device 100 with additionaldata. For example, the search system 104 may transmit link (e.g., textand/or image) data that the user device 100 may use to generate the userselectable links for the result object data included in the searchresults. Each user selectable link may include a portion of the linkdata that the user of the user device 100 may select (e.g., touch, or“click on”). Each user selectable link may also be associated with thecorresponding result object data included in the search results, suchthat when the user selects the link, the user device 100 accesses thecontent (e.g., one or more files) specified by the data, or launches anative or web-based app referenced by the associated AM(s) and causesthe app to perform one or more operations indicated by the AM(s). Insome examples, the portion of the link data included in a particularuser selectable link may indicate the content accessed or operationsperformed by the user device 100 in response to the user selecting thelink.

As described herein, the search system 104 uses data included in (e.g.,records stored in) the search data store 110 to generate search resultsbased on search queries received from the user device 100. The searchdata store 110 may include one or more databases, indices (e.g.,inverted indices), tables, files, or other data structures that may beused to implement the techniques of the present disclosure. In someexamples, the search data store 110 may be included in one or morestorage devices. The search data store 110 includes one or more records(e.g., as shown in FIG. 6). Each record may include data related tonative apps, native app states, websites (e.g., web pages), documents,and/or media (e.g., audio, video, and/or image) files. For example, eachrecord may include, among other content, a record name/identifier (ID),record information, and result object data, which are described ingreater detail with reference to FIG. 6.

As described herein, the search system 104 receives the search queryfrom the user device 100 and generates the search results based on thequery. The search query may include text, numbers, and/or symbols (e.g.,punctuation) entered into the user device 100 by the user via voiceinput. For example, the user may have entered the search query into theuser device 100 via voice input using a search app included on thedevice 100. In some examples, the search app may be a native appdedicated to search. In other examples, the search app may be a moregeneral app, such as a web browser app also included on the user device100.

In some examples, the user device 100 may transmit additional data tothe search system 104 along with the search query. The search query andthe additional data may be referred to herein as a query wrapper. Theadditional data may include geo-location data associated with the userdevice 100, platform data for the device 100 (e.g., a type and/or aversion of the device 100, an OS, and/or a web browser app of the device100), an identity of the user (e.g., a username), partner specific data,and other data. The user device 100 may transmit the query wrapper tothe search system 104. The search system 104 may use the search queryand/or the additional data included in the query wrapper to generate thesearch results and transmit the results to the user device 100.

As described herein, to generate the search results, search module 108may identify one or more records included in the search data store 110based on the search query. Initially, the search module 108 may analyzethe search query. The search module 108 may then identify one or morerecords included in the search data store 110 based on the (e.g.,analyzed) search query. For example, the search module 108 may identifythe records based on (e.g., text) matches between terms of the searchquery and terms of information included in the records. The searchmodule 108 may then process (e.g., score) the identified records. Forexample, the search module 108 may determine how well the identifiedrecords match the search query. The search module 108 may then selectone or more of the identified records that best match the search query.The search module 108 may transmit record names/IDs associated with theselected records to the result generation module 112. The resultgeneration module 112 may identify the records selected by the searchmodule 108 in the search data store 110 using the received recordnames/IDs. The result generation module 112 may then select resultobject data from the identified records. The result generation module112 may transmit the selected result object data to the user device 100as the search results.

In some examples, the result generation module 112 may transmitadditional information with the result object data to the user device100. For example, as described herein, a set processing module of thesearch module 108 may generate result scores for the records from whichthe result object data is selected (e.g., using values of metricsassociated with persons, places, or things described in the recordsand/or various features of the search query). As such, the result objectdata selected from each record may be associated with a result scorethat indicates a rank of the data relative to result object dataselected from other records. In these examples, the result generationmodule 112 may transmit the result scores associated with the resultobject data to the user device 100 with the data. In other examples, theresult generation module 112 may transmit link (e.g., text and/or image)data associated with the result object data to the user device 100 to beused to display the data to the user, as also described herein.

The search system 104 may use various sources of data to generate and/orupdate the search data store 110. For example, the search system 104 mayuse the data sources to generate and/or update one or more databases,indices, tables, files, or other data structures included in the searchdata store 110. For instance, the search system 104 may generate newrecords and update existing records using data retrieved from the datasources. Although not shown, the search system 104 may include one ormore modules configured to generate the new records and/or update theexisting records. In some examples, some or all of the data included inthe search data store 110 (e.g., one or more records) may be manuallygenerated by a human operator.

The data sources may include a variety of different data providers. Forexample, the data sources may include providers (e.g., publishers) ofwebsites (e.g., web pages), documents, and/or media (e.g., audio, video,and/or image) files. In some examples, the data sources may also includedata from app developers, such as app developer websites and data feedsprovided by app developers. The data sources may also include operatorsof digital distribution platforms configured to distribute apps to userdevices 100. The data sources may further include other websites, suchas websites that include web logs (i.e., blogs), app reviews, or otherdata related to apps. Additionally, the data sources may include socialnetworking sites, such as “FACEBOOK®” by Facebook Inc. (e.g., Facebookposts) and “TWITTER®” by Twitter Inc. (e.g., text from tweets). The datasources may also include online databases that include data related tomovies, television programs, music, and restaurants, and other types ofdata sources having various types of content and update rates. In someexamples, the search system 104 may retrieve data from the data sources,including any type of data described herein. The search system 104 maythen generate one or more records based on the data and store therecords in the search data store 110. In other examples, some or all ofthe data included in the records (e.g., record information) may bemanually generated by a human operator. In further examples, the dataincluded in the records may be updated over time so that the searchsystem 104 provides up-to-date search results in response to searchqueries received from the user device 100.

FIG. 4 is a functional block diagram of an example user device 100 incommunication with one or more users 428 and/or a search system 104. Asshown in FIG. 4, the user device 100 includes one or more processingunits 400, memory components 402, input/output (I/O) components 404, andinterconnect components 406. The memory component(s) 402 store an OS408, a web browser app 410, one or more native apps 412 (e.g., nativeapps installed on the user device 100), and a search app 414. As alsoshown, the user device 100 further includes a pressure-sensitive display102 including a pressure input detection module 416 and a finger contactinput detection module 418, an ambient light detection module 420, acovered user interaction detection module 422, a covered userinteraction response module 424, and a search result handling module426. For example, the pressure-sensitive display 102 may correspond toany of a liquid crystal display (LCD), a plasma display, a cathode-raydisplay, and another display type included in the user device 100. Thepressure input detection module 416 may correspond to any of a resistivetouchscreen, a push-button-based touchscreen, and anotherpressure-sensitive sensor or input device and any associated hardware,firmware, and/or software included in the pressure-sensitive display102. In some examples, the pressure input detection module 416 maycorrespond to a capacitive touchscreen configured to sense pressureinputs (e.g., via changes in distance and, as a result, capacitancebetween multiple membranes of the touchscreen due to pressure applied tothe touchscreen) any associated hardware, firmware, and/or softwareincluded in the pressure-sensitive display 102. The finger contact inputdetection module 418 may correspond to any of a capacitive touchscreenand another finger contact-sensitive sensor or input device and anyassociated hardware, firmware, and/or software included in thepressure-sensitive display 102. The ambient light detection module 420may correspond to any of an ambient light sensor, a video and/or stillimage camera, and another input device included in the user device 100(e.g., in the presence-sensitive display 102) and configured to detectan amount of ambient light incident upon the device 100 (e.g., upon thedisplay 102). The covered user interaction detection module 422, covereduser interaction response module 424, and search result handling module426 may each be implemented by the processing unit(s) 400 executingcomputer-readable instructions stored in the memory component(s) 402,causing the unit(s) 400 to interact with any of the resources describedherein with reference to the user device 100, and/or with any of theuser(s) 428, the search system 104, and other computing devices. Asdescribed herein, in some examples (not shown), the user device 100 mayfurther include an accelerometer sensor configured to provide outputsthat indicate pressure inputs received at (e.g., force applied to) thepressure-sensitive display 102.

The processing unit(s) 400 may be configured to execute instructionsstored in the memory component(s) 402 and communicate with the memorycomponent(s) 402 and I/O component(s) 404 (e.g., via the interconnectcomponent(s) 406). Each of the OS 408, web browser app 410, nativeapp(s) 412, and search app 414 may be embodied in computer-executable,or computer-readable, instructions and executed by the processingunit(s) 400. The memory component(s) 402 may further storecomputer-executable, or computer-readable, instructions associated with(e.g., used to operate) one or more of the pressure-sensitive display102, pressure input detection module 416, finger contact input detectionmodule 418, ambient light detection module 420, covered user interactiondetection module 422, covered user interaction response module 424, andsearch result handling module 426, which may also be executed by theprocessing unit(s) 400. The memory component(s) 402 may also beconfigured to store system parameters and other data. Each of the I/Ocomponent(s) 404 may be configured to (e.g., at the direction of theprocessing unit(s) 400) receive inputs (e.g., pressure inputs 206,finger contact inputs 202, 204, search queries 430 as user voice inputs,and/or search results 432) to the user device 100 and transmit outputs(e.g., user prompts, search queries 430 as text strings, text-to-speechor playback outputs, and/or forwarded search results 432) from thedevice 100. The interconnect component(s) 404 (e.g., a bus) may beconfigured to provide communication between the processing unit(s) 400,memory component(s) 402, and I/O component(s) 404, as well as amongother systems or devices included within the user device 100 and/orlocated outside of the device 100 (e.g., the search system 104 and/orother computing devices).

The units, components, and modules of the user device 100 depicted inFIG. 4 may enable the device 100 to perform the techniques attributed tothe device 100 in this disclosure. For example, the user device 100(e.g., the processing unit(s) 400 executing instructions stored in thememory component(s) 402) may be configured to receive (e.g., via the I/Ocomponent(s) 404) pressure inputs 206 from the user(s) 428 at thepressure-sensitive display 102 and determine that the display 102 iscovered. The user device 100 (e.g., the processing unit(s) 400 executinginstructions stored in the memory component(s) 402) may be furtherconfigured to provide (e.g., via the I/O component(s) 404) user promptsto the user(s) 428 and receive (e.g., via the I/O component(s) 404 andsearch app 414) search queries 430 from the user(s) 428 via voice input.For example, the user device 100 may be configured to receive the searchqueries 430 from the user(s) 428 via a voice input module (not shown)configured to receive voice inputs from the user(s) 428 and convert themto one or more text strings via speech recognition techniques. The userdevice 100 (e.g., the processing unit(s) 400 executing instructionsstored in the memory component(s) 402) may also be configured totransmit (e.g., via the I/O component(s) 404) the search queries 430 tothe search system 104, receive (e.g., via the I/O component(s) 404)search results 432 from the system 104, and perform an action associatedwith the results 432.

The processing unit(s) 400 may execute one or more instructions includedin the memory component(s) 402 to perform one or more of receiving thepressure inputs 206 from the user(s) 428, determining that thepressure-sensitive display 102 is covered, providing the user prompts tothe user(s) 428, receiving the search queries 430 from the user(s) 428,transmitting the queries 430 to the search system 104, receiving thesearch results 432 from the system 104, and performing the actionassociated with the results 432. For example, the processing unit(s) 400may execute instructions associated with one or more of the OS 408, webbrowser app 410, native app(s) 412, search app 414, pressure-sensitivedisplay 102, pressure input detection module 416, finger contact inputdetection module 418, ambient light detection module 420, covered userinteraction detection module 422, covered user interaction responsemodule 424, and search result handling module 426. In a specificexample, the processing unit(s) 400 may execute instructions that causethe user device 100 to run the OS 408. To receive the pressure inputs206 from the user(s) 428, the processing unit(s) 400 may executeinstructions that cause the user device 100 to operate the pressureinput detection module 416 of the pressure-sensitive display 102. Inadditional examples, the user device 100 may be further configured toreceive finger contact inputs 202, 204 from the user(s) 428, e.g., viathe processing unit(s) 400 executing instructions that cause the device100 to operate the finger contact input detection module 418. Todetermine that the pressure-sensitive display 102 is covered, theprocessing unit(s) 400 may execute instructions that cause the userdevice 100 to operate the covered user interaction detection module 422.As described herein, in some examples, to make this determination, theprocessing unit(s) 400 may execute instructions that cause the userdevice 100 to operate the ambient light detection module 420. To providethe user prompts to the user(s) 428, receive the search queries 430 fromthe user(s) 428 via voice input, transmit the queries 430 to the searchsystem 104, and receive the search results 432 from the system 104, theprocessing unit(s) 400 may further execute instructions that cause theuser device 100 to operate the covered user interaction response module424 and run one or more of the web browser app 410, native app(s) 412,and search app 414, e.g., within the OS 408. For example, to provide theuser prompts to the user(s) 428, the processing unit(s) 400 may executeinstructions that cause the user device 100 to operate a sound and/orvibration output module (not shown). To receive the search queries 430from the user(s) 428, transmit the queries 430 to the search system 104,and receive the search results 432 from the system 104, the processingunit(s) 400 may execute instructions that cause the user device 100 torun the search app 414, which may be an app dedicated to search, or anyof the web browser app 410 and native app(s) 412 (e.g., a more generalapp).

To perform the action associated with the search results 432, theprocessing unit(s) 400 may execute instructions that cause the userdevice 100 to operate the search result handling module 426. As aresult, as one example, the user device 100 may display the searchresults 432 to the user(s) 428 at the pressure-sensitive display 102. Asanother example, the user device 100 may provide text-to-speech orplayback outputs for the search results 432 to the user(s) 428. As stillanother example, the user device 100 may forward the search results 432(e.g., via any of a wireless and a wired communications network orprotocol) to one or more (e.g., proximate) other computing devices,e.g., for display and/or text-to-speech or playback output.

FIG. 5A illustrates an example of the search system 104. As describedherein, the search system 104 generates search results 432 based on asearch query 430 received from the user device 100 and using dataincluded in the search data store 110. Specifically, the search module108 identifies one or more records included in the search data store 110based on the search query 430. The search module 108 then transmits oneor more record names/IDs 500 that identify the identified records to theresult generation module 112. The result generation module 112 receivesthe record names/IDs 500 from the search module 108, identifies therecords in the search data store 110 using the names/IDs 500, andselects result object data from the identified records. The resultgeneration module 112 then transmits the selected result object data tothe user device 100 as the search results 432 (e.g., with result scores,link data, and/or other data).

FIG. 5B illustrates examples of the search module 108 and search datastore 110. The search module 108 of FIG. 5B includes a query analysismodule 502, a consideration set generation module (hereinafter, “setgeneration module”) 504, and a consideration set processing module(hereinafter, “set processing module”) 506. The query analysis module502 receives a search query 430 from the user device 100 (e.g., as partof a query wrapper) and analyzes the query 430 (e.g., performs any oftokenization, filtering, stemming, synonymization, and stop word removalwith respect to the query 430). The set generation module 504 identifiesone or more records included in the search data store 110 based on the(e.g., analyzed) search query 430 (e.g., using information retrievalsoftware, such as Lucene® developed by the Apache Software Foundation).The set generation module 504 may identify the records based on one ormore (e.g., text) matches between one or more terms of the search query430 and one or more terms of information (e.g., record names/IDs and/orrecord information) included in the records. The identified records maybe referred to herein as a “consideration set.” The set processingmodule 506 may process (e.g., score and select a subset of) theconsideration set, select one or more record names/IDs 500 from therecords of the set that identify some or all of the records, andtransmit the names/IDs 500 to the result generation module 112.

The information conveyed by the search results 432 may depend on themanner in which the set processing module 506 generates the resultscores for the records. For example, for each record, the correspondingresult score may indicate relevance of the information specified by therecord to the search query 430, popularity of the information, or otherproperties of the information, depending on the one or more parametersthe set processing module 506 uses to score the records. The setprocessing module 506 may generate the result scores for the records ina variety of different ways. In some examples, the set processing module506 generates a result score for a record based on one or more scoringfeatures. The scoring features may be associated with the record and/orthe search query 430. A record scoring feature may be based on any dataassociated with a record. For example, a record scoring feature may bebased on any data included in record information of a record. Examplerecord scoring features may be a quality score, or whether the recordincludes an AAM that specifies a default app state (e.g., a main page ofa native app), or a deeper app state. A query scoring feature mayinclude any data associated with the search query 430. For example, aquery scoring feature may include a number of words in the search query430, popularity of the query 430, and an expected frequency of the wordsin the query 430. A record-query scoring feature may include any datagenerated based on information associated with both a record and thesearch query 430 that resulted in identification of the record by theset generation module 504. For example, record-query scoring featuresmay include parameters that indicate how well terms of the search query430 match terms of record information of the identified record.According to the disclosed techniques, the set processing module 506 maygenerate a result score for a record based on a record, query,record-query, and/or any additional scoring features not explicitlylisted.

In some examples, the set processing module 506 may include one or moremachine-learned models (e.g., a supervised learning model) configured toreceive one or more scoring features. The machine-learned models maygenerate one or more result scores based on at least one of the record,query, and record-query scoring features described herein. For example,the set processing module 506 may pair the search query 430 with eachrecord and calculate a vector of features for each (query, record) pair.The vector of features may include one or more record, query, andrecord-query scoring features. The set processing module 506 may theninput the vector of features into a machine-learned relevance (MLR)model (e.g., including regression) to calculate a result score for therecord. In some examples, the MLR model may include a set of decisiontrees (e.g., gradient-boosted decision trees), or may be trained by asimple form of logistic regression. In other examples, themachine-learned task described herein can be framed as a semi-supervisedlearning task, where a minority of the training data is labeled withhuman curated result scores and the rest of the data is used withoutsuch labels.

As described herein, the result scores associated with the records(e.g., the information included therein) may be used in a variety ofdifferent ways. In some examples, the result scores may be used to rank(e.g., order) the corresponding result object data within a list. Inthese examples, a higher result score may indicate that thecorresponding result object data (e.g., information) is more relevant tothe user (e.g., to the search query 430) than result object data havinga smaller result score. In examples where the search results 432 aredisplayed as a list of user selectable links at the user device 100 oranother computing device, the links including result object dataassociated with larger result scores may be listed closer to the top ofthe list (e.g., near the top of the screen). In these examples, thelinks including result object data having lower result scores may belocated farther down the list (e.g., off screen) and may be accessed byscrolling down the screen of the user device 100 or other computingdevice.

FIG. 6 depicts an example record 600 that may be included in the searchdata store 110. The record 600 of FIG. 6 includes (e.g., specifies)information related to any of native apps, native app states, websites(e.g., web pages), documents, and/or media (e.g., audio, video, and/orimage) files, as described herein. As shown in FIG. 6, the record 600includes a record name/ID 602 that uniquely identifies the record 600among other records 600 included in the search data store 110. Asfurther shown, the record 600 also includes record information 604(e.g., text) that describes the information, or content, included in(e.g., specified by) the record 600. As also shown, the record 600further includes result object data 606 that corresponds to theinformation, or content, included in (e.g., specified by) the record600. For example, as shown, the result object data 606 may include orindicate one or more files, including text, image, audio, and/or videodata. As further shown, the result object data 606 may include one ormore AMs (e.g., AAMs, WAMs, and/or ADAs) that enable a user device 100to access app states of native or web-based apps, as described herein.

In some examples, the record 600 of FIG. 6 may also include informationthat describes values of one or more metrics associated with a person,place, or thing described in the record 600. Example metrics include thepopularity of a place described in the record 600 and/or ratings (e.g.,user ratings) of the place. For example, if the record 600 describes asong, a metric associated with the song may be based on the popularityof the song and/or ratings (e.g., user ratings) of the song. Theinformation included in the record 600 may also be based on measurementsassociated with the record 600, such as how often the record isretrieved during a search and how often user selectable links forinformation specified by the record 600 are selected by a user. Theinformation may also indicate whether the record 600 includes an AAM fora default app state, or a deeper app state, of a native app.

FIGS. 7A-7C are flow diagrams that illustrate example methods 700A-700C,respectively, for performing a search at a user device 100 in responseto receiving a pressure input 206 at a pressure-sensitive display 102 ofthe device 100 and determining that the display 102 is covered. Withreference to FIG. 7A, in block 702A, a user device 100 may initiallyreceive a pressure input 206 from a user of the device 100 at apressure-sensitive display 102 of the device 100. In block 704A, theuser device 100 (e.g., the covered user interaction detection module422) may determine that the pressure-sensitive display 102 is covered.As described herein, the user device 100 determining that thepressure-sensitive display 102 is covered may include the device 100determining that the display 102 is obscured from the user's view by oneor more layers of clothing (e.g., due to the device 100 being locatedunder the user's sleeve or in the user's pocket) or by other objects.For example, the user device 100 may determine that thepressure-sensitive display 102 is covered before, during (e.g., inresponse to), and/or after receiving the pressure input 206 from theuser. As one example, with reference to FIG. 7B, in block 702B, the userdevice 100 may determine that the pressure input 206 does not coincidewith a finger contact input 202, 204 received substantiallycontemporaneously with the pressure input 206 from the user at (e.g., acapacitive touchscreen included in) the pressure-sensitive display 102and, in block 704B, determine that the display 102 is covered based onthis determination. Additionally (e.g., in combination with thedetermination described above), or alternatively, with reference to FIG.7C, in block 702C, the user device 100 may receive an output from anambient light sensor (or, e.g., a camera, or another input device) ofthe device 100. In this example, the output may indicate an amount ofambient light present at the pressure-sensitive display 102. In block704C, the user device 100 may further determine that thepressure-sensitive display 102 is covered based on the output from theambient light sensor (e.g., determine that the amount of ambient lightpresent at the pressure-sensitive display 102, as indicated by theoutput, is below a threshold amount).

In block 706A, the user device 100 (e.g., the covered user interactionresponse module 424) may optionally, in response to receiving thepressure input 206 and determining that the pressure-sensitive display102 is covered, provide a user prompt (e.g., a sound and/or vibrationoutput) to the user. For example, the user prompt may be configured toprompt the user to provide a search query 430 to the user device 100 viavoice input. In block 708A, the user device 100 (e.g., the covered userinteraction response module 424) may, in response to receiving thepressure input 206 and determining that the pressure-sensitive display102 is covered (and, e.g., in response to and subsequent to providingthe user prompt), receive the search query 430 from the user via voiceinput. For example, the user device 100 may allow the user to providethe search query 430 via voice input within a predefined amount of timeafter the device 100 provides the user prompt to the user. In someexamples, the user device 100 may receive the search query 430 from theuser via the search app 414 included on the device 100.

In block 710A, the user device 100 (e.g., the covered user interactionresponse module 424) may transmit the search query 430 to the searchsystem 104 via the network 106 (e.g., as part of a query wrapper). Inthis example, the search system 104 may receive the search query 430from the user device 100 and generate one or more search results 432based on the query 430. As described herein, the search results 432 mayinclude result object data specifying content related to any of nativeapps, native app states, websites (e.g., web pages), documents, and/ormedia (e.g., audio, video, and/or image) files, as well as one or moreresult scores and link data. The search system 104 may then transmit thesearch results 432 to the user device 100. In block 712A, the userdevice 100 (e.g., the covered user interaction response module 424) mayreceive the search results 432, including the result object data andother information, from the search system 104 subsequent (e.g., inresponse) to transmitting the search query 430 to the system 104. Inblock 714A, the user device 100 (e.g., the search result handling module426) may perform an action associated with the search results 432. Asone example, the user device 100 may display one or more of the searchresults 432 to the user at the pressure-sensitive display 102. Asanother example, the user device 100 may provide a text-to-speech and/orplayback output for one or more of the search results 432. As stillanother example, the user device 100 may forward one or more of thesearch results 432 to another computing device (e.g., for display ortext-to-speech and/or playback output, in a similar manner as describedherein).

FIG. 8 is a flow diagram that illustrates an example method 800 forperforming a search for one or more records 600 included in the searchdata store 110 using a search query 430 received from a user device 100.As shown in FIG. 8, in block 802, the search system 104 may initiallyreceive a search query 430 specified by a user from a user device 100(e.g., as part of a query wrapper). As described with reference to FIG.7A, the user device 100 may receive the search query 430 from the userand transmit the query 430 to the search system 104 upon receiving apressure input 206 at a pressure-sensitive display 102 of the device 100and determining that the display 102 is covered. In some examples, thesearch system 104 may also receive other information from the userdevice 100 (e.g., as part of the query wrapper, or separately), such asinformation associated with the user and/or geo-location, platform, andIP address information associated with the device 100. In block 804, thesearch system 104 (e.g., the query analysis module 502) may optionallyperform an analysis of the search query 430 (e.g., perform any oftokenization, filtering, stemming, synonymization, and stop word removalwith respect to the query 430). In block 806, the search system 104(e.g., the set generation module 504) may identify a consideration setof one or more records 600 included in the search data store 110 basedon the (e.g., analyzed) search query 430. In this example, eachidentified record 600 may specify any of a variety of information,including content related to native apps, native app states, websites(e.g., web pages), documents, and/or media (e.g., audio, video, and/orimage) files. Also in this example, the search system 104 (e.g., the setgeneration module 504) may identify the records 600 based on one or morematches between one or more terms of the search query 430 and one ormore terms of information (e.g., record names/IDs 602 and/or recordinformation 604) included in the records 600.

In blocks 808-810, the search system 104 (e.g., the set processingmodule 506) may optionally process the consideration set of records 600.Specifically, in block 808, the search system 104 may generate one ormore result scores for the records 600 included in the considerationset. For example, the search system 104 may generate a result score foreach record 600 included in the consideration set. In block 810, thesearch system 104 may select one or more (e.g., a subset of the) records600 from the consideration set based on the one or more result scoresassociated with the selected records 600. For example, the search system104 may select one or more records 600 having the highest (e.g.,largest) one or more result scores. In block 812, the search system 104(e.g., the result generation module 112) may select result object datafrom the (e.g., selected) records 600 of the consideration set. Forexample, the search system 104 may select information relating to any ofnative apps, native app states, websites, documents, and/or media filesfrom each (e.g., selected) record 600. In some examples, the searchsystem 104 may also select other information from the (e.g., selected)records 600, such as result scores and/or link data associated with therecords 600. In block 814, the search system 104 (e.g., the resultgeneration module 112) may generate one or more search results 432 thatinclude the selected result object data. For example, the search system104 may generate the search results 432 such that each result 432includes the result object data selected from one of the (e.g.,selected) records 600 of the consideration set. In block 816, the searchsystem 104 (e.g., the result generation module 112) may transmit thesearch results 432, including the selected result object data and anyother information, to the user device 100.

FIGS. 9A-10B illustrate example GUIs that may be generated on a userdevice 100 and other computing devices according to this disclosure. Theuser device 100 shown in FIGS. 9A-10A is a wrist watch computing device(e.g., a smart watch) including watch straps. Example wrist watchcomputing devices include the SAMSUNG GALAXY GEAR®, the SAMSUNG GALAXYGEAR® 2, the SAMSUNG GEAR® 2 Neo, and the SAMSUNG GEAR FIT® developed bySamsung Electronics Co., Ltd., as well as the APPLE WATCH® developed byApple Inc. FIG. 10B depicts another computing device 1000 (e.g., asmartphone). As described herein, the user device 100 includes apressure-sensitive display 102 configured to receive pressure inputs 206from users of the device 100. As also described herein, thepressure-sensitive display 102 may also be (e.g., may include acapacitive touchscreen) configured to receive finger contact inputs 202,204 (e.g., finger taps and/or swipes) from the users.

As shown in FIG. 9A, the user device 100 receives a pressure input 206from a user of the device 100 at the pressure-sensitive display 102.Upon receiving the pressure input 206, the user device 100 furtherdetermines that the pressure-sensitive display 102 is covered. As oneexample, as described herein, the user device 100 may determine that thepressure input 206 does not coincide with any finger contact inputs 202,204 received substantially contemporaneously with the pressure input 206at (e.g., the capacitive touchscreen included in) the pressure-sensitivedisplay 102. As another example, as also described herein, the userdevice 100 may receive an output from an ambient light sensor includedin the device 100 and determine that the pressure-sensitive display 102is covered based on the received output (e.g., based on an amount ofambient light present at the display 102, as indicated by the output,such as an amount that is below a threshold amount). As previouslyexplained, in some examples, the user device 100 may determine that thepressure-sensitive display 102 is covered prior to, during (e.g., inresponse to), or following receiving the pressure input 206.

As shown in FIG. 9B, upon receiving the pressure input 206 anddetermining that the pressure-sensitive display 102 is covered, the userdevice 100 may optionally provide a user prompt to the user. Forexample, as also shown, the user prompt may be configured to requestthat the user provide a search query 430 to the user device 100 viavoice input. For instance, the user prompt may include one or more of avibration, a tone, a soundbite, and a voice command output prompting theuser to provide the search query 430 to the user device 100 via voiceinput (e.g., as indicated by the speaker GUI element shown in FIG. 9B).In this example, upon receiving the pressure input 206 and determiningthat the pressure-sensitive display 102 is covered (and, e.g., inresponse to the user prompt), the user device 100 receives the searchquery 430 from the user and transmits the query 430 to a search system104.

As shown in FIG. 9C, the user device 100 receives one or more searchresults 432 from the search system 104 subsequent to transmitting thesearch query 430 and performs an action associated with the results 432.As one example, as also shown, the user device 100 displays the searchresults 432 to the user (e.g., as results 1−N, where N is an integervalue greater or equal to 1) on the pressure-sensitive display 102.Additionally, or alternatively, as also shown, the user device 100provides a text-to-speech and/or playback output for the search results432 to the user (e.g., as indicated by the speaker GUI element shown inFIG. 9C). In still other examples, as shown in FIGS. 10A-10B, the userdevice 100 may forward the search results 432 for display ortext-to-speech and/or playback output to the other computing device1000.

The modules and data stores included in the user device 100 and searchsystem 104 represent features that may be included in these devices andsystems as they are described in the present disclosure. For example,the processing unit(s) 400, memory component(s) 402, I/O component(s)404, interconnect component(s) 406, pressure-sensitive display 102,ambient light detection module 420, covered user interaction detectionmodule 422, covered user interaction response module 424, search resulthandling module 426, and the various contents thereof may representfeatures included in the user device 100. Similarly, the search module108, search data store 110, result generation module 112, and thevarious contents thereof may represent features included in the searchsystem 104. The modules and data stores described herein may be embodiedby electronic hardware, software, and/or firmware components. Depictionof different features as separate modules and data stores does notnecessarily imply whether the modules and data stores are embodied bycommon or separate electronic hardware, software, and/or firmwarecomponents. As such, in some implementations, the features associatedwith the one or more modules and data stores depicted herein may berealized by common or separate electronic hardware, software, and/orfirmware components.

The modules and data stores may be embodied by electronic hardware,software, and/or firmware components, including one or more processingunits, memory components, I/O components, and interconnect components.The interconnect components may be configured to provide communicationbetween the processing units, memory components, and I/O components. Forexample, the interconnect components may include one or more busesconfigured to transfer data between electronic components. Theinterconnect components may also include control circuits (e.g., amemory controller and/or an I/O controller) configured to controlcommunication between electronic components.

The processing units may include one or more central processing units(CPUs), graphics processing units (GPUs), digital signal processingunits (DSPs), or other processing units. The processing units may beconfigured to communicate with the memory components and I/O components.For example, the processing units may be configured to communicate withthe memory components and I/O components via the interconnectcomponents.

A memory component (memory) may include any volatile or non-volatilemedia. For example, the memory may include electrical media, magneticmedia, and/or optical media, such as a random access memory (RAM),read-only memory (ROM), non-volatile RAM (NVRAM), electrically-erasableprogrammable ROM (EEPROM), Flash memory, hard disk drives (HDDs), solidstate drives (SSDs), magnetic tape drives, optical storage technology(e.g., compact disc, digital versatile disc, and/or Blu-ray disc), orany other memory components. The memory components may include (e.g.,store) the data described herein. For example, the memory components mayinclude data used by the user device 100, data included in the record(s)600 of the search data store 110, and/or other data. The memorycomponents may also include instructions executed by the processingunits. For example, the memory components may include computer-readableinstructions that, when executed by the processing units, cause theunits to perform the various functions attributed to the modules anddata stores described herein.

The I/O components may refer to electronic hardware, software, and/orfirmware providing communication with a variety of different devices.For example, the I/O components may provide communication between otherdevices and the processing units and memory components. In someexamples, the I/O components may be configured to communicate with acomputer network. For example, the I/O components may be configured toexchange data over a computer network using a variety of differentphysical connections, wireless connections, and protocols. The I/Ocomponents may include network interface components (e.g., a networkinterface controller), repeaters, network bridges, network switches,routers, and firewalls. In some examples, the I/O components may includehardware, software, and/or firmware configured to communicate withvarious human interface devices, including (e.g., pressure-sensitive)display screens, keyboards, pointer devices (e.g., a mouse), (e.g.,capacitive, resistive, push-button-based, and/or other) touchscreens,speakers, and microphones. In some examples, the I/O components mayinclude hardware, software, and/or firmware configured to communicatewith additional devices, such as external memory (e.g., external HDDs).

In some implementations, the search system 104 may be a system of one ormore computing devices (e.g., a computer search system) configured toimplement the techniques described herein. Put another way, the featuresattributed to the modules and data stores described herein may beimplemented by one or more computing devices. Each computing device mayinclude any combination of the electronic hardware, software, and/orfirmware described herein. For example, each computing device mayinclude any combination of the processing units, memory components, I/Ocomponents, and interconnect components described herein. The computingdevices may also include various human interface devices, includingdisplay screens, keyboards, pointing devices (e.g., a mouse),touchscreens, speakers, and microphones. The computing devices may alsobe configured to communicate with additional devices, such as externalmemory (e.g., external HDDs).

The computing devices of the search system 104 may be configured tocommunicate with the network 106. The computing devices may also beconfigured to communicate with one another via a computer network. Insome examples, the computing devices may include one or more servercomputing devices configured to communicate with the user device 100(e.g., receive search queries 430 and transmit search results 432),gather data from data sources, index the data, store the data, and storeother documents or media. In some examples, the computing devices mayreside within one or more machines at a single geographic location. Inother examples, the computing devices may be distributed across a numberof geographic locations.

What is claimed is:
 1. A computing device comprising: apressure-sensitive display configured to receive contact inputs from auser of the computing device and pressure inputs, wherein each pressureinput of the pressure inputs is indicative of at least a predeterminedpressure being applied to the pressure-sensitive display, and whereineach contact input of the contact inputs is indicative of direct contactof an electrically conductive object with the pressure-sensitivedisplay; a network interface component configured to communicate with anetwork; one or more memory components configured to storecomputer-readable instructions; and one or more processing unitsconfigured to execute the computer-readable instructions, wherein thecomputer-readable instructions include: in response to receiving a firstpressure input of the pressure inputs from the user at thepressure-sensitive display, determining that the first pressure inputcorresponds to the pressure-sensitive display being covered in responseto none of the contact inputs being received when the first pressureinput is received; in response to determining that the first pressureinput corresponds to the pressure-sensitive display being covered,transmitting a search query to a search system via the network using thenetwork interface component; receiving search results from the searchsystem in response to transmitting the search query; and performing anaction associated with the search results.
 2. The computing device ofclaim 1, wherein the computer-readable instructions further include, inresponse to determining that the first pressure input corresponds to thepressure-sensitive display being covered, providing a user prompt to theuser, wherein the user prompt comprises one or more of a sound outputand a vibration output.
 3. The computing device of claim 1, wherein thepressure-sensitive display includes a capacitive touchscreen configuredto receive the contact inputs from the user.
 4. The computing device ofclaim 1, further comprising: an ambient light sensor configured totransmit an output indicating an amount of ambient light incident on thepressure-sensitive display, wherein the computer-readable instructionsinclude: receiving the output from the ambient light sensor, anddetermining that the pressure-sensitive display is covered in responseto the output indicating the ambient light is below a threshold.
 5. Thecomputing device of claim 1, wherein the computer-readable instructionsinclude displaying the search results to the user at thepressure-sensitive display.
 6. The computing device of claim 1, whereinthe computer-readable instructions include playing the search results tothe user using text-to-speech.
 7. The computing device of claim 1,wherein the computer-readable instructions include forwarding the searchresults to another computing device.
 8. The computing device of claim 1,further comprising: an accelerometer sensor configured to transmit anoutput indicating an amount of force applied to the computing device bythe user, wherein the computer-readable instructions include receivingat least some of the pressure inputs based on the output from theaccelerometer sensor.
 9. The computing device of claim 1, wherein thecomputing device comprises one or more of a smartphone computing device,a smart watch computing device, and a fitness band computing device. 10.A method comprising: selectively receiving pressure inputs via apressure-sensitive display of a user device, wherein each pressure inputof the pressure inputs is indicative of at least a predeterminedpressure being applied to the pressure-sensitive display; selectivelyreceiving contact inputs from a user of the user device via thepressure-sensitive display, wherein each contact input of the contactinputs is indicative of direct contact of an electrically conductiveobject with the pressure-sensitive display; in response to receiving afirst pressure input of the pressure inputs at the pressure-sensitivedisplay, determining, by the user device, that the first pressure inputcorresponds to the pressure-sensitive display being covered in responseto none of the contact inputs being received when the first pressureinput is received; in response to determining that the first pressureinput corresponds to the pressure-sensitive display being covered,transmitting, from the user device, a search query to a search systemvia a network; at the user device, receiving search results from thesearch system in response to transmitting the search query; and by theuser device, performing an action associated with the search resultsusing the user device.
 11. The method of claim 10, further comprising,in response to determining that the first pressure input corresponds tothe pressure-sensitive display being covered, providing a user promptfrom the user device to the user, wherein the user prompt includes oneor more of a sound output and a vibration output.
 12. The method ofclaim 10, wherein determining that the pressure-sensitive display iscovered comprises: receiving an output from an ambient light sensor ofthe user device, wherein the output indicates an amount of ambient lightincident on the pressure-sensitive display; and determining that thepressure-sensitive display is covered further based on the output beingbelow a threshold.
 13. The method of claim 10, wherein the actionassociated with the search results includes displaying the searchresults to the user on the pressure-sensitive display.
 14. The method ofclaim 10, wherein receiving the one of the pressure inputs at thepressure-sensitive display comprises: receiving an output from anaccelerometer sensor of the user device, wherein the output indicates anamount of force applied to the user device by the user; and receiving atleast some of the pressure inputs based on the output from theaccelerometer sensor.
 15. A non-transitory computer-readable mediumcomprising instructions for execution by one or more processing units ofa user device, wherein the instructions include: selectively receivingpressure inputs via a pressure-sensitive display of the user device,wherein each pressure input of the pressure inputs is indicative of atleast a predetermined pressure being applied to the pressure-sensitivedisplay; selectively receiving contact inputs from a user of the userdevice via the pressure-sensitive display, wherein each contact input ofthe contact inputs is indicative of direct contact of an electricallyconductive object with the pressure-sensitive display; in response toreceiving a first pressure input of the pressure inputs at thepressure-sensitive display, determining that the first pressure inputcorresponds to the pressure-sensitive display being covered in responseto none of the contact inputs being received when the first pressureinput is received; in response to determining that the first pressureinput corresponds to the pressure-sensitive display being covered,transmitting a search query to a search system via a network; receivingsearch results from the search system in response to transmitting thesearch query; and performing an action associated with the searchresults using the user device.
 16. The computer-readable medium of claim15, wherein the instructions include receiving the search query viavoice input from the user subsequent to providing the user prompt. 17.The computing device of claim 2, wherein the computer-readableinstructions further include receiving the search query via voice inputfrom the user subsequent to providing the user prompt.
 18. The method ofclaim 11, further comprising receiving the search query via voice inputfrom the user subsequent to providing the user prompt.
 19. The method ofclaim 10, wherein the action associated with the search results includesaudibly reading the search results to the user using text-to-speech. 20.The method of claim 10, wherein the action associated with the searchresults includes forwarding the search results to another computingdevice.